Messaging system apparatuses circuits and methods of operation thereof

ABSTRACT

A messaging system may include a messaging client device that may be configured to receive an impermanent text message and may be further configured to manage the impermanent text message in accordance with a message management policy associated with the impermanent text message. The messaging system may further include an impermanent messaging server configured to validate the messaging client device as complying with the message management policy prior to authorizing a transmission of the impermanent text message to the messaging client device. The messaging system may include a distributed network gateway server configured to validate the messaging client device as complying with a message management policy prior to authorizing transmission of the impermanent text message to the messaging client device.

FIELD OF THE INVENTION

The present invention generally relates to a messaging system,apparatuses circuits and methods of operation thereof. Morespecifically, the present invention relates to a messaging systemwherein one or more of the messages contain message attributes, definingthe characteristics of parameters such as the message's lifespan,accessibility and/or functionality.

BACKGROUND

More than 2.5 billion text messages are sent in the U.S. daily, withconsumers often using text messages or e-mails to replace casualconversation and businesses increasingly relying on mobile messaging asmeans of instructing and updating staff with regard to enterpriserelated matters. Various other messaging platforms and techniques havebeen developed and are in the works. However, a common deficiency of allknown current messaging types and platforms is that once a message hasbeen sent out and was received at a recipient device, no furtherintervention by the sender relating to any of the message's content andcharacteristics can be made.

Taking the above into account, there clearly remains a need for betterand more efficient messaging systems, apparatuses, circuits and methodsof operation thereof, that may allow for the expiration (e.g. deletion)of a message and/or the manipulation of a message's characteristics(e.g. functionality limitation) after it was received at itsdestination.

SUMMARY OF THE INVENTION

Below are described a number of novel, innovative features of amessaging system, apparatuses circuits and methods of operation thereof.

The present invention is a messaging system, apparatuses circuits andmethods of operation thereof. A message, in accordance with someembodiments of the present invention, may comprise one or more messageattributes, defining the characteristics of parameters such as itslifespan, accessibility and/or functionality. The message attributes mayinclude, for example, limitations relating to the time duration throughwhich the message may be accessed, the number of times the message maybe accessed, the geographical area in which the message may be accessed,the ability to print the message, the ability to save the message, theability to forward the message and/or any other way in which themessage's functionality may be limited.

According to some embodiments of the present invention, the messageattributes may be defined/authored by a user of a sending client device.According to some embodiments of the present invention, a messagingserver may append and/or add additional message attributes to a message,and/or edit message attributes defined/authored by the user of thesending client device. According to some embodiments of the presentinvention, a message authoring application may allow for the user of thesending client device to compose and/or edit the message's content andattributes.

According to some embodiments of the present invention, one or moremessage attributes policies each comprising one or more messagefunctionality limitations may be defined. The message attributespolicies may be enforced based, for example, on characteristics such asmessage content and/or recipient group/position.

According to some embodiments of the present invention, an enforcementmodule may be adapted to enforce the message attributes. According tosome embodiments, a receiving client device may comprise an enforcementmodule adapted to enforce the message attributes on some or all of itsincoming messages. The enforcement module may erase and/or limit thefunctionality of a given message based on its message attributes,substantially at the time of receipt and/or as certain attribute definedthreshold(s) is/are met (e.g. delete the message once a certain amountof time has passed from its time of receipt). According to someembodiments of the present invention, the messaging server may comprisean authentication module and/or a verification module adapted toauthenticate the receiving client device and/or to verify its messageattribute enforcement capabilities (e.g. the existence/functionality ofits enforcement module circuit/application), prior to forwarding amessage to it.

According to some embodiments of the present invention, the messagingserver may send the receiving client device a floating agent applicationinstallation file, adapted to install itself on the receiving clientdevice and to enforce the message attributes, prior to forwarding themessage to it. Once a floating agent application installationnotification, confirming the installation of the floating agent on thereceiving client device, is received by the messaging server, the servermay proceed to forward the message to the receiving client device. Thenow installed floating agent application may enforce the messageattributes.

According to some embodiments of the present invention, relating todirect device to device communications, for example, peer to peer typenetworks; the sending client device may comprise an authenticationmodule and/or a verification module adapted to authenticate thereceiving client device and/or to verify its message attributeenforcement capabilities (e.g. the existence/functionality of itsenforcement module circuit/application). Once the receiving clientdevice has been authenticated/verified, the sending client device maysend the message directly to it. The receiving client device's policyenforcement module may issue an expiration, functionality-limitationand/or deletion command upon expiration of one or more of the message'sexpiration attributes.

According to some embodiments of the present invention, the messagingserver may comprise an enforcement module adapted to enforce the messageattributes on some or all of its incoming messages. The enforcementmodule may erase and/or limit the functionality of a given message basedits message attributes, substantially at the time of receipt and/or ascertain attribute defined threshold(s) is/are met (e.g. delete themessage once a certain amount of time has passed from its time ofreceipt). The messaging server may comprise a message page generationand storage module adapted to generate and store a browser renderablecode (e.g. HTML page, WAP page), herein code includes message content.The messaging server may then send the receiving client device a link tothe message content including page. The messaging server's enforcementmodule may check and possibly update a given message's attribute(s)intermittently (e.g. as time to expiration and deletion of a message isdecreasing), each time the page including the message is linked (e.g. asthe number of attribute allowed message views decreases with eachlinkage to it) and/or as a result of an external intervention by anadministrator/owner using an attribute update/management module, of themessaging server, adapted to allow for deleting, editing and/orappending message attributes and/or message attribute policies. Uponexpiration of one or more message attributes, and possibly the deletionof the message, a message deletion/expiration notification may be sendto the receiving client device by the messaging server.

According to some embodiments of the present invention, an attributecontaining message may be encrypted by the sending client device priorto its sending. The message may be decrypted by the receiving clientdevice, by the messaging server or by combination of both the clientreceiving device and the messaging server (e.g. server holds publicdecryption keys, server acts as the certificate authority).

According to some embodiments of the present invention, exemplary systemconfigurations for handling and communicating impermanent and/orfunction-limiting attribute(s) containing messages may include: directdevice to device communication configurations; configurations whereinclient devices may directly send/receive impermanent/function-limitingmessages to each other. Impermanent/function-limiting messagingfunctionality enforcement verification data is initially communicatedover one or more cellular and/or one or more distributed networksbetween the two client devices; configurations wherein some or all ofthe messaging system functionalities may be implemented on a cellularand/or distributed network's gateway or gatekeeper server(s);configurations wherein cellular network gateways compriseimpermanent/function-limiting messaging functionality; configurationswherein client devices of one or more cellular networks and/ordistributed networks may send/receive impermanent/function-limitingmessages to each other; configurations wherein client devices ofdifferent cellular networks may send/receiveimpermanent/function-limiting messages to each other; configurationwherein client devices of similar and/or different enterprise networksmay send/receive impermanent/function-limiting messages to each other;and direct device to device communication configurations (e.g. peer topeer) wherein each sending and/or receiving device may compriseimpermanent/function-limiting messaging functionality, andsending/receiving client devices may be adapted to fallback to adistributed network (e.g. Internet, cellular) and/or an enterprisecommunication network, when direct transmission functionality isunavailable.

BRIEF DESCRIPTION OF THE DRAWINGS

The subject matter regarded as the invention is particularly pointed outand distinctly claimed in the concluding portion of the specification.The invention, however, both as to organization and method of operation,together with objects, features, and advantages thereof, may best beunderstood by reference to the following detailed description when readwith the accompanying figures:

In FIG. 1 there is shown, in accordance with some embodiments of thepresent invention, an exemplary structure of a message;

In FIG. 2 there is shown, in accordance with some embodiments of thepresent invention, a sending client device comprising a messageauthoring application for authoring message content and/or messagehandling attributes;

In FIG. 3A-3C there are shown, in accordance with some embodiments ofthe present invention, a message authoring application residing on thesending client device (3A), on the messaging server (3B) and/or onanother dedicated or non-dedicated networked authoring server (3C)accessible by the sending client device;

In FIG. 4 there is shown, in accordance with some embodiments of thepresent invention, an exemplary configuration in which a messagingserver (e.g. an enterprise messaging server) is adapted to allow formessage attributes policies definition and updating;

In FIG. 5A there is shown, in accordance with some embodiments of thepresent invention, an exemplary configuration where the receiving clientdevice is adapted to enforce the message attributes;

In FIG. 5B there is shown, in accordance with some embodiments of thepresent invention, an exemplary configuration where the messaging serveris adapted to send the receiving client device a floating agentapplication for enforcing the message attributes;

In FIG. 5C there is shown, in accordance with some embodiments of thepresent invention, an exemplary configuration where two client devicesare adapted to send messages directly to one another;

In FIG. 5D there is shown, in accordance with some embodiments of thepresent invention, an exemplary configuration where the messaging servercomprises a message attribute enforcement module;

In FIG. 5E there is shown, in accordance with some embodiments of thepresent invention, an exemplary configuration where the client devicescomprise message attribute enforcement modules and the sending clientdevice is adapted to verify the receiving client device's ability toenforce message attributes by use of the messaging server;

In FIG. 5F there is shown, in accordance with some embodiments of thepresent invention, an exemplary configuration where an attribute(s)containing message may be sent directly from the sending client deviceto the receiving client device, in an encrypted form;

In FIG. 5G there is shown, in accordance with some embodiments of thepresent invention, an exemplary configuration where an attribute(s)containing message may be sent from the sending client device to themessaging server, in an encrypted form;

In FIG. 5H there is shown, in accordance with some embodiments of thepresent invention, an exemplary configuration where an attribute(s)containing message may be sent from the sending client device to themessaging server, in an encrypted form; and

In FIGS. 6A-6G there are shown, in accordance with some embodiments ofthe present invention, a few exemplary system(s) and network(s)configurations for handling and communicating impermanent and/orfunction-limiting attribute(s) containing messages.

DETAILED DESCRIPTION

In the following detailed description, numerous specific details are setforth in order to provide a thorough understanding of the invention.However, it will be understood by those skilled in the art that thepresent invention may be practiced without these specific details. Inother instances, well-known methods, procedures, components and circuitshave not been described in detail so as not to obscure the presentinvention.

Unless specifically stated otherwise, as apparent from the followingdiscussions, it is appreciated that throughout the specificationdiscussions utilizing terms such as “processing”, “computing”,“calculating”, “determining”, or the like, refer to the action and/orprocesses of a computer or computing system, or similar electroniccomputing device, that manipulate and/or transform data represented asphysical, such as electronic, quantities within the computing system'sregisters and/or memories into other data similarly represented asphysical quantities within the computing system's memories, registers orother such information storage, transmission or display devices.

Embodiments of the present invention may include apparatuses forperforming the operations herein. Such apparatus may be speciallyconstructed for the desired purposes, or it may comprise ageneral-purpose computer selectively activated or reconfigured by acomputer program stored in the computer. Such a computer program may bestored in a computer readable storage medium, such as, but is notlimited to, any type of disk including floppy disks, optical disks,CD-ROMs, magnetic-optical disks, read-only memories (ROMs), randomaccess memories (RAMs) electrically programmable read-only memories(EPROMs), electrically erasable and programmable read only memories(EEPROMs), magnetic or optical cards, or any other type of mediasuitable for storing electronic instructions, and capable of beingcoupled to a computer system bus.

The processes and displays presented herein are not inherently relatedto any particular computer or other apparatus. Various general-purposesystems may be used with programs in accordance with the teachingsherein, or it may prove convenient to construct a more specializedapparatus to perform the desired method. The desired structure for avariety of these systems will appear from the description below. Inaddition, embodiments of the present invention are not described withreference to any particular programming language. It will be appreciatedthat a variety of programming languages may be used to implement theteachings of the inventions as described herein.

The present invention is a messaging system, apparatuses circuits andmethods of operation thereof. A message, in accordance with someembodiments of the present invention, may comprise one or more messageattributes, defining the characteristics of parameters such as itslifespan, accessibility and/or functionality. The message attributes mayinclude, for example, limitations relating to the time duration throughwhich the message may be accessed, the number of times the message maybe accessed, the geographical area in which the message may be accessed,the ability to print the message, the ability to save the message, theability to forward the message and/or any other way in which themessage's functionality may be limited.

In FIG. 1 there is shown, in accordance with some embodiments of thepresent invention, an exemplary structure of a message comprising: themessage's content, the recipient designator(s), the message expirationattributes, message attribute enforcement policies defining the scope ofenforcement and the message functionalities to be limited as attributethreshold(s) are met. It is made clear that a message, in accordancewith some embodiments of the present invention, may be sent to one ormore recipients or receiving client devices and may contain or haveattachments containing any type of content(s) (e.g. text, images, video,audio). According to some embodiments, as part of limiting a givenmessage's functionality, the quality of one or more of itscontained/attached content(s) (e.g. text, images, video, audio) may bedegraded. Furthermore, the terms ‘message’ and/or ‘impermanent message’,as used hereinafter, may relate to any message or type of messageassociated with one or more attribute(s) and/or policy(ies), whichattribute(s) and/or policy(ies) may define the characteristics of one ormore parameters such as the message's lifespan, accessibility and/orfunctionality.

According to some embodiments of the present invention, the messageattributes may be defined/authored by a user of a sending client device.According to some embodiments of the present invention, a messagingserver may append and/or add additional message attributes to a message,and/or edit message attributes defined/authored by the user of thesending client device. According to some embodiments of the presentinvention, a message authoring application may allow for the user of thesending client device to compose and/or edit the message's content andattributes.

In FIG. 2 there is shown, in accordance with some embodiments of thepresent invention, a sending client device comprising a messageauthoring application for authoring message content and/or messagehandling attributes. A networked messaging server may edit and/orappend, or allow for editing and/or appending of, message content and/ormessage handling attributes. A recipient selection module may select oneor more recipients or append one or more designators of recipients towhich the message is intended (e.g. based on a selection made by themessage author/sender). A transmit module may then send the message toone or a group of receiving client devices, corresponding to selectedrecipient(s), within the same network or on another accessible network.According to some embodiments, the message may be sent to the receivingclient device in a ‘push’ mode or, alternatively, a notificationinforming the receipt of a new message at the server may be sent to thereceiving client device, which receiving device may then ‘pull’ themessage from the server. According to some embodiments, the messagingserver may comprise a database for storing messages sent to receivingclient devices which are not available (e.g. not connected to theserver/in a no reception zone/not online) or for storing messagesdelivered in ‘pull’ mode, awaiting for receiving client deviceretrieval.

In FIG. 3A-3C there are shown, in accordance with some embodiments ofthe present invention, a message authoring application residing on thesending client device (3A), on the messaging server (3B) and/or onanother dedicated or non-dedicated networked authoring server (3C)accessible by the sending client device. According to some embodiments,message authoring applications may reside on more than one of the abovementioned devices/servers.

According to some embodiments of the present invention, one or moremessage attributes policies each comprising one or more messagefunctionality limitations may be defined. The message attributespolicies may be enforced based, for example, on characteristics such asmessage content and/or recipient group/position. In FIG. 4 there isshown, in accordance with some embodiments of the present invention, anexemplary configuration in which a messaging server (e.g. an enterprisemessaging server) is adapted to allow for message attributes policiesdefinition and updating. Recipient group/position based policies may beenforced based on the receiving client device(s)' designator(s) providedby the receiving client device(s), whereas message content basedpolicies may be enforced based on the content of given messages asreceived by the messaging server, prior to their forwarding to thereceiving device(s). A policy update module may be adapted to allow forthe definition and/or updating of policies (e.g. by anadministrator/owner/sender), from within the messaging server's networkand/or from another network or networked administrator/ownercomputerized device which are connected to the messaging server'snetwork.

According to some embodiments of the present invention, an enforcementmodule may be adapted to enforce the message attributes. According tosome embodiments, a receiving client device may comprise an enforcementmodule adapted to enforce the message attributes on some or all of itsincoming messages. The enforcement module may erase and/or limit thefunctionality of a given message based on its message attributes,substantially at the time of receipt and/or as certain attribute definedthreshold(s) is/are met (e.g. delete the message once a certain amountof time has passed from its time of receipt). According to someembodiments of the present invention, the messaging server may comprisean authentication module and/or a verification module adapted toauthenticate the receiving client device and/or to verify its messageattribute enforcement capabilities (e.g. the existence/functionality ofits enforcement module circuit/application), prior to forwarding amessage to it.

In FIG. 5A there is shown, in accordance with some embodiments of thepresent invention, an exemplary configuration where the receiving clientdevice is adapted to enforce the message attributes. A message from asending client device is received by the messaging server, the messagingserver then sends a policy enforcement verification request to thereceiving client device. Upon receipt of a policy enforcementauthentication reply, the messaging server proceeds to forward themessage content and attributes to the receiving client device. When oneor more of the message's attributes are expired, the receiving clientdevice notifies the messaging server by sending it a messagedeletion/expiration notification. Both, the messaging server and thereceiving client device may then issue deletion/expiration and/orcorresponding functionality limitation commands to their respectivecontrol modules, which commands either delete completely or limit thefunctionality of their respective message copies. According to someembodiments, the messaging server may optionally initiate thedeletion/expiration and/or function limitation of a message, and may beadapted to accordingly instruct the client device(s).

According to some embodiments of the present invention, the messagingserver may send the receiving client device a floating agent applicationinstallation file, adapted to install itself on the receiving clientdevice and to enforce the message attributes, prior to forwarding themessage to it. Once a floating agent application installationnotification, confirming the installation of the floating agent on thereceiving client device, is received by the messaging server, the servermay proceed to forward the message to the receiving client device. Thenow installed floating agent application may enforce the messageattributes.

In FIG. 5B there is shown, in accordance with some embodiments of thepresent invention, an exemplary configuration where the messaging serveris adapted to send the receiving client device a floating agentapplication for enforcing the message attributes. A message from asending client device is received by the messaging server, the messagingserver then sends a floating agent application installation file to thereceiving client device. Upon receipt of a floating agent applicationinstallation confirmation, the messaging server proceeds to forward themessage content and attributes to the receiving client device. When oneor more of the message's attributes are expired, the floating agentapplication issues a notice and the receiving client device notifies themessaging server by sending it a message deletion/expirationnotification. Both, the messaging server and the receiving client devicemay then issue deletion/expiration and/or corresponding functionalitylimitation commands to their respective control modules, which commandseither delete completely or limit the functionality of their respectivemessage copies.

According to some embodiments of the present invention, relating todirect device to device communications, for example, peer to peer typenetworks; the sending client device may comprise an authenticationmodule and/or a verification module adapted to authenticate thereceiving client device and/or to verify its message attributeenforcement capabilities (e.g. the existence/functionality of itsenforcement module circuit/application). Once the receiving clientdevice has been authenticated/verified, the sending client device maysend the message directly to it. The receiving client device's policyenforcement module may issue an expiration, functionality-limitationand/or deletion command upon expiration of one or more of the message'sexpiration attributes.

In FIG. 5C there is shown, in accordance with some embodiments of thepresent invention, an exemplary configuration where two client devicesare adapted to send messages directly to one another. The sending clientdevice may send to the receiving client device a policy enforcementverification request. Upon receipt and verification/authentication ofthe receiving client device's policy enforcement authentication reply,the sending client device may proceed to send it the message content andattributes.

According to some embodiments of the present invention, the messagingserver may comprise an enforcement module adapted to enforce the messageattributes on some or all of its incoming messages. The enforcementmodule may erase and/or limit the functionality of a given message basedits message attributes, substantially at the time of receipt and/or ascertain attribute defined threshold(s) is/are met (e.g. delete themessage once a certain amount of time has passed from its time ofreceipt). The messaging server may comprise a message page generationand storage module adapted to generate and store a browser renderablecode (e.g. HTML page, WAP page), herein code includes message content.The messaging server may then send the receiving client device a link tothe message content including page. The messaging server's enforcementmodule may check and possibly update a given message's attribute(s)intermittently (e.g. as time to expiration and deletion of a message isdecreasing), each time the page including the message is linked (e.g. asthe number of attribute allowed message views decreases with eachlinkage to it) and/or as a result of an external intervention by anadministrator/owner using an attribute update/management module, of themessaging server, adapted to allow for deleting, editing and/orappending message attributes and/or message attribute policies. Uponexpiration of one or more message attributes, and possibly the deletionof the message, a message deletion/expiration notification may be sendto the receiving client device by the messaging server.

In FIG. 5D there is shown, in accordance with some embodiments of thepresent invention, an exemplary configuration where the messaging servercomprises a message attribute enforcement module. A message from asending client device is received by the messaging server and a messagepage (e.g. webpage) is generated and stored by a message page generationand storage module, functionally associated with the enforcement module.A link to the message page is then sent to the receiving client devicewhich may use it access the message page and its content. Uponexpiration of one or more of the message attributes a messagedeletion/expiration command may be sent by the enforcement module to themessage page generation and storage module, the message page generationand storage module may, in response, delete, remove or else wise limitthe functionality and/or accessibility of the message including page andits included content. A message expiration notification may then be sentto the receiving client device, informing its user of thedeletion/removal/limitation of functionality.

In FIG. 5E there is shown, in accordance with some embodiments of thepresent invention, an exemplary configuration where the client devicescomprise message attribute enforcement modules and the sending clientdevice is adapted to verify the receiving client device's ability toenforce message attributes by use of the messaging server. The sendingclient device may initially send the message recipient designator to themessaging server. Based on the recipient designator the messaging servermay send an enforcement verification request to the receiving clientdevice. Upon receipt of an enforcement authentication reply themessaging server may send a receiving client device authenticationmessage to the sending client device that may now proceed and send themessage.

According to some embodiments of the present invention, an attributecontaining message may be encrypted by the sending client device priorto its sending. In FIG. 5F there is shown, in accordance with someembodiments of the present invention, an exemplary configuration wherean attribute(s) containing message may be sent directly from the sendingclient device to the receiving client device, in an encrypted form. Thereceiving client device may then send a self-verification request to themessaging server, receive in return an enforcement verification requestand reply to it with an enforcement authentication reply authenticatingits ability to enforce message attribute/attribute policies. Once themessaging server's authentication module and/or verification module haveauthenticated and verified the receiving client device as messageattribute enforcement capable, the receiving client device may send thereceived message's encryption attributes to the messaging server andreceive, in return, the corresponding message decryption key(s) to beused by its decryption module to decrypt the encrypted message. Furtherenforcement of the message attributes may be handled by the receivingclient device enforcement module.

In FIG. 5G there is shown, in accordance with some embodiments of thepresent invention, an exemplary configuration where an attribute(s)containing message may be sent from the sending client device to themessaging server, in an encrypted form. The messaging server may thensend an enforcement verification request to the receiving client deviceand receive in response an enforcement authentication reply. Once themessaging server's authentication module and/or verification module haveauthenticated and verified the receiving client device as messageattribute enforcement capable, it may use its decryption module todecrypt the encrypted message and send it to the receiving clientdevice. Further enforcement of the message attributes may be handled bythe receiving client device enforcement module.

In FIG. 5H there is shown, in accordance with some embodiments of thepresent invention, an exemplary configuration where an attribute(s)containing message may be sent from the sending client device to themessaging server, in an encrypted form. The messaging server may thensend an enforcement verification request to the receiving client deviceand receive in response an enforcement authentication reply. Once themessaging server's authentication module and/or verification module haveauthenticated and verified the receiving client device as messageattribute enforcement capable, it may forward the encrypted message tothe receiving client device may use its decryption module, possiblyusing one or more decryption keys it possesses to decrypt the encryptedmessage. Further enforcement of the message attributes may be handled bythe receiving client device enforcement module.

In FIGS. 6A-6G there are shown, in accordance with some embodiments ofthe present invention, a few exemplary system(s) and network(s)configurations for handling and communicating impermanent and/orfunction-limiting attribute(s) containing messages.

In FIG. 6A there is shown, in accordance with some embodiments of thepresent invention, a direct device to device communication configuration(e.g. peer to peer) wherein each sending and/or receiving device maycomprise impermanent/function-limiting messaging functionality.

In FIG. 6B there is shown, in accordance with some embodiments of thepresent invention, a communication configuration wherein client devicesmay directly send/receive impermanent/function-limiting messages to eachother. Impermanent/function-limiting messaging functionality enforcementverification data is initially communicated over one or more cellularand/or one or more distributed networks between the two client devices.Upon authentication of the receiving client device asimpermanent/function-limiting messaging functionality capable, themessage is directly sent to it by the sending client device. All suchmessages may thus be subject to impermanent/function-limiting messagingfunctionality handling and enforcement.

According to some embodiments of the present invention, some or all ofthe messaging system functionalities may be implemented on a cellularand/or distributed network's gateway or gatekeeper server(s).Accordingly, a gateway or gatekeeper server may comprise an authoringapplication module, an attribute enforcement module and/or native clientattribute enforcement verification/authentication module(s) adapted toverify native client devices' compliance with message attributesenforcement, prior to the forwarding of attribute containing messages tothem.

In FIG. 6C there is shown, in accordance with some embodiments of thepresent invention, a communication configuration wherein cellularnetwork gateways comprise impermanent/function-limiting messagingfunctionality. A message being sent from a cellular networked device orfrom an Internet networked device must pass through one of the cellularnetwork gateways, prior to being communicated over the cellular networkto one or more receiving client devices, and is thus subject toimpermanent/function-limiting messaging functionality handling andenforcement.

In FIG. 6D there is shown, in accordance with some embodiments of thepresent invention, a communication configuration wherein client devicesof one or more cellular networks and/or distributed networks maysend/receive impermanent/function-limiting messages. A message from adistributed network's sending client device is sent through thedistributed network's messaging server having animpermanent/function-limiting messaging functionality. The message isthen sent to a cellular network Internet gateway and from there, overthe cellular network to the cellular receiving client device. A messagefrom a cellular client to a distributed network client may first be sentover the cellular network to the cellular network Internet gateway andto the distributed network receiving client device through the messagingserver. All such messages may thus be subject toimpermanent/function-limiting messaging functionality handling andenforcement.

In FIG. 6E there is shown, in accordance with some embodiments of thepresent invention, a communication configuration wherein client devicesof different cellular networks may send/receiveimpermanent/function-limiting messages to each other. Two or more NativeSMS/MMS gateways/servers may comprise enforcementverification/authentication modules adapted to verify the ability of thereceiving client device's cellular network gateways to handle andenforce impermanent/function-limiting messaging functionality. Onceenforcement capability has been verified, the message may be sent to thereceiving client device through its cellular gateway having verifiedimpermanent/function-limiting messaging functionality. All such messagesmay thus be subject to impermanent/function-limiting messagingfunctionality handling and enforcement.

In FIG. 6F there is shown, in accordance with some embodiments of thepresent invention, a communication configuration wherein client devicesof similar and/or different enterprise networks may send/receiveimpermanent/function-limiting messages to each other. A given clientdevice may initially send a message to its own enterprise's enterprisemessaging server, where the message's content and/or attributes may beedited and/or additional content and/or attributes may be appended. Themessage may then be sent to a policy and attributeenforcement/verification server adapted to either enforce the message'sattributes and/or related enterprise policies, or to verify thereceiving client device(s)' ability to enforce the message's attributesand/or related enterprise policies. The message may then be sent to thereceiving client device(s), which receiving client device(s) may be partof either the same enterprise's network or part of another enterprisenetwork.

In FIG. 6G there is shown, in accordance with some embodiments of thepresent invention, a direct device to device communication configuration(e.g. peer to peer) wherein each sending and/or receiving device maycomprise impermanent/function-limiting messaging functionality. In thisexemplary configuration, sending/receiving client devices may be adaptedto fallback to a distributed network (e.g. Internet, cellular) and/or anenterprise communication network, when direct transmission functionalityis unavailable. It is made clear that various additionalimpermanent/function-limiting messaging fallback-enabling configurationsmay be practiced. Impermanent/function-limiting messaging functionalitymay thus be implemented on two or more communication levels/networks,wherein a first level serves as a default communication configurationand one or more additional levels function as fallback communicationconfiguration(s) for scenarios where the default level is unavailable.Furthermore, moving from one Impermanent/function-limiting messagingcommunication configuration to another may be partially or fully basedon aggregative communication optimization factors (e.g. availabletransmission bandwidth).

While certain features of the invention have been illustrated anddescribed herein, many modifications, substitutions, changes, andequivalents will now occur to those skilled in the art. It is,therefore, to be understood that the appended claims are intended tocover all such modifications and changes as fall within the true spiritof the invention.

What is claimed is:
 1. A messaging system comprising: a first mobilemessaging client device executing a messaging application and associatedwith a first authorized user, the mobile messaging client device havinga processor configured to: a) receive from a messaging server anotification of the presence of a message at the messaging server, wherethe message is addressed to the first authorized user; b) send to themessaging server a request to retrieve the message, the requestincluding client authentication data, where the first mobile messagingclient device sends the request automatically in response to receipt ofthe notification; c) receive the message, the message having messagecontent; d) manage the message in accordance with a message attribute,wherein managing the message comprises limiting a functionality of themessage based on the message attribute, where the message and themessage attribute are stored in non-volatile memory in the first mobilemessaging client device at least until the message is managed by thefirst mobile messaging device in accordance with the message attribute;and e) send to the messaging server a message management notification;the messaging server having a processor configured to: a) receive themessage addressed to the first authorized user from a second mobilemessaging client device executing the messaging application andassociated with a second authorized user; b) store the message in adatabase; c) transmit to the first mobile messaging client device thenotification of the presence of the message at the messaging server; d)receive from the first mobile messaging client device the request toretrieve the message, the request including client authentication data;e) validate the first mobile messaging client device based on the clientauthentication data; f) transmit the message to the first mobilemessaging client device; and g) receive from the first mobile messagingclient device the message management notification.
 2. The system ofclaim 1, wherein the message management notification is sent from thefirst mobile messaging client device after the first mobile messagingclient device manages the message and indicates the first mobilemessaging client device managed the message in accordance with themessage attribute.
 3. The system of claim 1, wherein the messageattribute is set by the second authorized user at the second mobilemessaging client device and is transmitted from the second mobilemessaging device to the first mobile messaging client device via themessaging server.
 4. The system of claim 1, wherein the messagemanagement notification is sent from the first mobile messaging clientdevice before the first mobile messaging client device manages themessage.
 5. The system of claim 1, wherein the message attribute furthercomprises a predetermined message deletion time, and the predeterminedmessage deletion time is based on a time the first mobile messagingclient device first displays the message.
 6. The system of claim 1,wherein the message attribute comprises a predetermined message viewingtime after which at least a portion of the message content cannot bedisplayed at the first mobile messaging device, and the predeterminedmessage viewing time is based on a time the first mobile messagingclient device first displays the message.
 7. The system of claim 1,wherein the message attribute further comprises a number of times themessage may be accessed at the first mobile messaging client device. 8.A messaging system comprising a messaging server having a processorconfigured to: a) receive a message from a second mobile messagingclient device executing a messaging application and associated with asecond authorized user; b) store the message in a database; c) transmitto a first mobile messaging client device executing the messagingapplication and associated with a first authorized user, a notificationof the presence of the message at the messaging server, where themessage is addressed to the first authorized user; d) receive from thefirst mobile messaging client device a request to retrieve the message,the request including client authentication data; e) validate the firstmobile messaging client device based on the client authentication data;f) transmit the message and a message attribute to the first mobilemessaging client device, where the message and the message attribute arestored in non-volatile memory in the first mobile messaging clientdevice at least until the message is managed by the first mobilemessaging device in accordance with the message attribute; and g)receive from the first mobile messaging client device a messagemanagement notification generated by the first mobile messaging clientdevice in connection with managing the message in accordance with themessage attribute at the first mobile messaging client device.
 9. Thesystem of claim 8, wherein the message management notification is sentfrom the first mobile messaging client device after the first mobilemessaging client device manages the message and indicates the firstmobile messaging client device managed the message in accordance withthe message attribute.
 10. The system of claim 8, wherein the messageattribute comprises a predetermined message viewing time after which atleast a portion of a content of the message cannot be displayed at thefirst mobile messaging device, and the predetermined message viewingtime is based on a time the first mobile messaging client device firstdisplays the message.
 11. The system of claim 8, wherein the messagingserver is further configured to: prior to f), receive the messageattribute from the second authorized user at the second mobile messagingclient device.
 12. The system of claim 8, wherein the messaging serveris further configured to: h) manage the message at the messaging serverin accordance with the message attribute.
 13. The system of claim 12,wherein in h) the messaging server deletes the message from thedatabase.
 14. The system of claim 8, wherein the message attributecomprises a predetermined message deletion time, and the predeterminedmessage deletion time is based on a time the first mobile messagingclient device first displays the message.
 15. The system of claim 8,wherein the message management notification is sent from the firstmobile messaging client device before the first mobile messaging clientdevice manages the message.
 16. The system of claim 8, wherein themessage attribute further comprises a number of times the message may beaccessed at the first mobile messaging client device.
 17. A method formanaging a messaging system comprising the steps of: a) receiving at amessaging server a message addressed to a first authorized user from asecond mobile messaging client device executing a messaging applicationand associated with a second authorized user; b) storing the message ina database; c) transmitting from the messaging server to a first mobilemessaging client device executing the messaging application andassociated with a first authorized user, a notification of the presenceof the message at the messaging server; d) receiving at the messagingserver from the first mobile messaging client device a request toretrieve the message, the request including client authentication data;e) validating the first mobile messaging client device at the messagingserver based on the client authentication data; f) transmitting themessage and a message attribute from the messaging server to the firstmobile messaging client device, where the message and the messageattribute are stored in non-volatile memory in the first mobilemessaging client device at least until the message is managed by thefirst mobile messaging device in accordance with the message attribute;g) managing the message in accordance with the message attribute at themessaging server; and h) receiving at the messaging server from thefirst mobile messaging client device a message management notificationgenerated by the first mobile messaging client device in connection withmanaging the message in accordance with the message attribute at thefirst mobile messaging client device.
 18. The method of claim 17,wherein the message attribute comprises a predetermined message viewingtime after which at least a portion of a content of the message cannotbe displayed at the first mobile messaging device, and the predeterminedmessage viewing time is based on a time the first mobile messagingclient device first displays the message.
 19. The method of claim 17,wherein the message notification is sent from the first mobile messagingclient device after the first mobile messaging client device manages themessage and indicates the first mobile messaging client device managedthe message in accordance with the message attribute.
 20. The method ofclaim 17, further comprising: prior to f), receiving the messageattribute from the second authorized user at the second mobile messagingclient device.
 21. The method of claim 17, wherein in step g) themessaging server deletes the message from the database.
 22. The methodof claim 17, wherein the message attribute comprises a predeterminedmessage deletion time, and the predetermined message deletion time isbased on a time the first mobile messaging client device first displaysthe message.
 23. The method of claim 17, wherein the message managementnotification is sent from the first mobile messaging client devicebefore the first mobile messaging client device manages the message. 24.The method of claim 17, wherein the message attribute comprises a numberof times the message may be accessed at the first mobile messagingclient device.